Flight crew connectivity systems and methods

ABSTRACT

Systems and methods according to one or more embodiments are provided for an aircraft flight crew secure communication path to multiple aircraft data domains. In one example, a system includes one or more data interface devices configured to communicate data. A power module is configured to provide power to the one or more data interface devices, and a switch coupled between the power module and each of the one or more data interface devices is configured to selectively provide power from the power module to at least one of the one or more data interface devices. A data transceiver is configured to couple to an external communication device, and a controller coupled between the one or more data interface devices and the data transceiver is configured to provide a data communication path between the selectively powered data interface device and the data transceiver for the external communication device.

TECHNICAL FIELD

One or more embodiments relate generally to aircraft systems, and moreparticularly, for example, to secure flight crew communicationconnectivity.

BACKGROUND

In the field of aircraft flight crew secure communication, there is anongoing effort to improve flight crew access to multiple levels ofnetwork communication security within the aircraft flight deck. Forexample, different data domains on an aircraft require different levelsof network access security and existing solutions that provide securenetwork access require complex, multiunit systems to meet networksecurity demands. Thus, there is a need to provide improved access tomultiple secure and unsecure data domains by the flight crew within anaircraft flight deck.

SUMMARY

Systems and methods are disclosed herein in accordance with one or moreembodiments that provide flight crew connectivity to multiple datadomains within an aircraft flight deck. In various embodiments, at leastone of one or more data interface devices, each coupled to a differentdata domain, is selectively powered and a dedicated data communicationpath is formed between the powered data interface device and a datatransceiver for communication with a flight crew communication device.Communication is possible with only the data domain coupled to theselectively powered data interface device. Network security is providedin that other data domains coupled to unpowered data interface devicesare not capable of communication on the data communication path.

In one example, a first data interface device is coupled to avionicsequipment where the avionics equipment provides aircraft control andaircraft information data. The selectively first powered data interfacedevice provides for physically isolating the aircraft control andaircraft information data on the data communication path between thepowered first data interface device and the data transceiver forcommunication with the flight crew communication device.

In another example, a second data interface device is coupled tonon-avionics equipment where the non-avionics equipment providespassenger information and entertainment data. The selectively secondpowered data interface device provides for physically isolating thepassenger information and entertainment data, and broadband interneeaccess on the data communication path between the powered second datainterface device and the data transceiver for communication with theflight crew communication device.

In one embodiment, a system includes one or more data interface devicesconfigured to communicate data; a power module configured to providepower to the one or more data interface devices; a switch coupledbetween the power module and each of the one or more data interfacedevices and configured to selectively provide power from the powermodule to at least one of the one or more data interface devices; a datatransceiver configured to couple to an external communication device;and a controller coupled between the one or more data interface devicesand the data transceiver and configured to provide a data communicationpath between the selectively powered data interface device and the datatransceiver for the external communication device.

In another embodiment, a method includes selectively switching powerfrom a power module to at least one of one or more data interfacedevices to selectively power the at least one data interface device;forming a data communication path between the selectively powered datainterface device and a data transceiver; and communicating data betweenthe at least one selectively powered data interface device and the datatransceiver for an external communication device.

The scope of the invention is defined by the claims, which areincorporated into this section by reference. A more completeunderstanding of embodiments of the invention will be afforded to thoseskilled in the art, as well as a realization of additional advantagesthereof, by a consideration of the following detailed description of oneor more embodiments. Reference will be made to the appended sheets ofdrawings that will first be described briefly.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a diagram of an aircraft including various aircraftdata domains and network interfaces, along with a flight crewconnectivity system, in accordance with one or more embodiments of thedisclosure.

FIG. 2 illustrates a block diagram of a flight crew connectivity systemin accordance with an embodiment of the disclosure.

FIG. 3 illustrates various data domains within an aircraft fuselage inaccordance with an embodiment of the disclosure.

FIG. 4 illustrates various functions of a flight crew connectivitysystem in accordance with embodiments of the disclosure.

FIG. 5 illustrates a panel concept display for a flight crewconnectivity system in accordance with embodiments of the disclosure.

FIGS. 6A-B illustrate flow diagrams describing a method for using aflight crew connectivity system in accordance with an embodiment of thedisclosure.

DETAILED DESCRIPTION

Systems and methods are provided in accordance with one or moreembodiments that provides for a flight crew personal electronic devicewith a secure wireless data communication connection to various datadomains integrated within an aircraft. In this regard, a flight crewconnectivity system provides for the flight crew personal electronicdevice to seamlessly connect to various aircraft data domains withdiffering levels of network access security without compromisingsecurity level requirements.

FIG. 1 illustrates a diagram of an aircraft 101 including a flight crewconnectivity system 100, various aircraft data domains, multipleaircraft network interfaces, and aircraft equipment connected to thenetwork interfaces in accordance with one or more embodiments of thedisclosure. Flight crew connectivity system 100 provides for a securewireless data communication path between a flight deck 110 of aircraft101 and various wired and wireless network protocols both onboard andoutside of aircraft 101. For example, flight crew connectivity system100 communicates with avionics equipment 102 onboard aircraft 101through wired communication interface 113, preferably via a secureaircraft protocol data bus such as ARINC 429 or ARINC 717. In someembodiments, flight crew connectivity system 100 communicates withnon-avionics equipment 104 through an Ethernet interface 115. In variousembodiments, flight crew connectivity system 100 wirelessly and securelyconnects components of avionics equipment 102 and non-avionics equipment104 with flight deck 110 via a secure wireless Wi-Fi network 103A-C. Insome embodiments, wireless Wi-Fi network 103A-C is a dedicated andsecure IEEE 802.11 service set identifier (SSID) airline proprietarylogin for flight crew personal electronic device use (e.g., such asflight crew personal electronic device 203 of FIG. 2) within flight deck110. Aircraft 101 includes an aircraft power module 106 (e.g., powersource) to provide power to flight crew connectivity system 100.

In some embodiments, flight crew connectivity system 100 is in wirelesscommunication with ground electronics 108 to provide for secure wirelesscommunications between ground electronics 108 and flight deck 110. Insome embodiments, ground electronics 108 wirelessly interfaces toaircraft 101 through airline proprietary secure IEEE 802.11 wirelessnetwork connection 103C, however other wireless network interfaces arepossible, such as an airline proprietary secure IEEE WiMAX 802.16wireless network connection. Flight crew personnel may downloadpredictive maintenance reports, and other data reports pertaining toaircraft 101 onto flight crew personal electronic device 203 from groundelectronics 108, for example. In some embodiments, flight crewconnectivity system 100 provides for a second secure wireless network119 for secure communication between personal electronic device 203 andan external cellular device (e.g., such as external cellular device 237Aof FIG. 2).

In various embodiments, avionics equipment 102 includes electronics foran aircraft information system and an aircraft control system. In someembodiments, electronics and circuitry for avionics equipment 102 isdistributed throughout aircraft 101. In some embodiments, avionicsequipment 102 provides for flight information and aircraft control data.In various embodiments, non-avionics equipment 104 includes electronicsfor passenger information systems and electronics and networks tointerface to passenger personal electronic devices. In some embodiments,non-avionics equipment 104 provides for aircraft maintenance data,aircraft operational performance data and other less secure flight crewapplications.

Aircraft 101 includes multiple connectivity protocols for connectingcomponents of avionics equipment 102 and non-avionic equipment 104. Insome embodiments, components of non-avionics equipment 104 utilize aWi-Fi communication network 105A-D to provide passengers within aircraftcabin 107 with broadband internet access. Passengers wirelessly connecttheir personal electronic devices (e.g., smartphones, tablets, laptopcomputers, for example) to the broadband internet through a broadbandKu/Ka band SATCOM antenna 109. Flight crew connectivity system 100provides for a secure data link between Wi-Fi communication network105A-D and flight deck 110 for flight crew personal electronic device203 to access broadband internet without compromising high levelsecurity requirements of aircraft 101 avionics equipment 102, asdiscussed herein.

FIG. 2 illustrates a block diagram of a flight crew connectivity system100 in accordance with an embodiment of the disclosure. Flight crewconnectivity system 100 includes a controller 201 (e.g., a media accesscontroller (MAC)/baseband processor), input data transceivers 211A-B(e.g., data interface devices), a wireless data transceiver 213 (e.g., adata transceiver, such as Wi-Fi, Bluetooth and NFC transceivers andantennas), a power module 217, and a domain switch 223.

Flight crew connectivity system 100 includes a power switch 219 (e.g.,power source switch) connected to aircraft power module 106. In someembodiments, power switch 219 is implemented as a single-pole,single-throw power switch connected to aircraft power module 106 at afirst terminal 219A and power module 217 at a second terminal 219B. Insome embodiments, power switch 219 is manually controlled at a displaypanel (e.g., such as display panel 500 of FIG. 5) to provide 115 voltsAC, 400 Hz to power module 217 connected to terminal 219B. However, inother embodiments, other aircraft power module 106 voltages andfrequencies are possible. In other embodiments, power switch 219 is asolid-state switch electrically controlled by an electrical signalprovided at display panel 500. In some embodiments, an indicator 225 isinstalled on display panel, and is implemented as a light emitting diode(LED). Indicator 225 is illuminated when power module 217 is powered onand providing power. In other embodiments, indicator 225 is implementedas an audible signal or other type of indicator to inform an operatorthat power module 217 is providing power. In some embodiments, powermodule 217 provides power directly to controller 201, wireless datatransceiver 213, a cellular transceiver 215 (e.g., cellular transceiver,SIM card and antenna), a Universal Serial Bus (USB) controller 231, anda secure digital (SD) card controller 232.

In various embodiments, power module 217 provides power to domain switch223. Domain switch 223 is implemented as a single-pole, double-throwswitch where an input terminal 223C is connected to power module 217. Afirst output terminal 223A is connected to a first input datatransceiver 211A (e.g., a first data interface device) at inputconnection 221A to provide power to first input data transceiver 211A. Asecond output terminal 223B is connected to a second input datatransceiver 211B (e.g., a second data interface device) at inputconnection 221B to provide power to second input data transceiver 211B.In other embodiments, domain switch 223 includes fewer or more outputterminals connected to fewer or more input data transceivers 211. In yetanother embodiment, domain switch 223 is implemented as a solid-stateswitch controlled by electrical 2Q signals provided at display panel500. The configuration of domain switch 223 (e.g., single-pole,double-throw) prevents first input data transceiver 211A and secondinput data transceiver 211B from being powered on at the same time inorder to provide for a physical isolation of data communicated fromfirst input data transceiver 211A and second input data transceiver 211Bon data buses 228A-F

First input data transceiver 211A is connected to avionics equipment 102by wired communication interface 113 and data bus 2210. In someembodiments, data bus 221C is implemented as an aircraft proprietaryARINC 429 data bus to complement wired communication interface 113. Inother embodiments, data bus 221C is implemented as an aircraftproprietary ARINC 717 data bus to complement wired communicationinterface 113. In yet another embodiment, data bus 221C is implementedas an Ethernet data bus to complement wired communication interface 113.In still another embodiment, data bus 221C is implemented as analogdiscrete signals to complement wired communication interface 113. Insome embodiments, components of avionics equipment 102 share one or moretypes of wired communication interface 113 implementations. In someembodiments, components of avionics equipment 102 include a flightmanagement computer, a display processor computer, a proximity sensorelectronics unit, a flight data acquisition unit, and an on-boardnetwork system. In other embodiments, fewer or more aircraft units areincluded in avionics equipment 102.

In some embodiments, second input data transceiver 211B is connected tonon-avionics equipment 104 (e.g., passenger Wi-Fi on/offboardconnectivity system) by Ethernet interface 115 and data bus 221Dimplemented as an Ethernet data bus to complement Ethernet interface115. In some embodiments, various components of non-avionics equipment104 share Ethernet interface 115. In some embodiments, non-avionicsequipment 104 includes components of a passenger information andentertainment system including an on-board Wi-Fi network 105A-D (seeFIG. 1) to provide broadband internet connectivity for passengerpersonal electronic devices (e.g., smartphones, tablets, laptopcomputers, etc.) through broadband Ku/Ka band SATCOM antenna 109, forexample.

Flight crew connectivity system 100 provides the ability for a securedata connection to aircraft information systems (e.g., as part ofavionics equipment 102), while also being able to provide a broadbandinternet connection via non-avionics equipment 104 over a common datacommunication path. This is due to domain switch 223, which providesphysical power isolation for avionics equipment 102 and non-avionicsequipment 104 when input data transceiver 211A or input data transceiver211B are selectively powered on. For example, when domain switch 223 iscontrolled to power-on first input data transceiver 211A, first inputdata transceiver 211A communicates with avionics equipment 102 tosecurely receive aircraft control and aircraft information data. Firstinput data transceiver 211A provides aircraft control and aircraftinformation data to controller 201 over data bus 228A.

In some embodiments, controller 201 is implemented to provide a datacommunication path between powered first input data transceiver 211A andwireless data transceiver 213 over data buses 228A and 228C. In otherembodiments, controller 201 is implemented to provide a datacommunication path between powered first input data transceiver 211A andUSB controller 231 over data buses 228A and 228E.

In some embodiments, when domain switch 223 is controlled to power onsecond input data transceiver 211B, second input data transceiver 211Bcommunicates with non-avionics equipment 104 to receive passengerinformation and entertainment data. Second input data transceiver 211Bprovides passenger information and entertainment data to controller 201over data bus 228B.

In some embodiments, controller 201 is implemented to provide a datacommunication path between powered second input data transceiver 211Band wireless data transceiver 213 over data buses 228B and 228C. Inother embodiments, controller 201 is implemented to provide a datacommunication path between powered second input data transceiver 211Band USB controller 231 over data buses 228B and 228E.

Aircraft control and aircraft information data is physically isolated ondata communication path 228A/228C and 228A/228E when first input datatransceiver 211A device is powered on and second input data transceiver211B is unpowered. In addition, broadband internet access and/orpassenger information and entertainment data is physically isolated ondata communication path 228B/228C and 228B/228E when second input datatransceiver 211B is powered on and first input data transceiver 211A isunpowered. In some embodiments, controller 201 is configured to identifythe selectively powered input data transceiver 211A/211B and communicatethe identification to the personal electronic device 203 (e.g., externalcommunication device). In various embodiments, a security level of thepersonal electronic device 203 comprises a single or multi-layered levelof security such as biometrics, pin, security badge, or other similarsecurity features and controller 201 is configured to validate thesecurity level of personal electronic device 203 (e.g., externalcommunication device).

In one embodiment, wireless data transceiver 213 is implemented with asecure Wi-Fi wireless network interface 213A to communicate betweenflight crew connectivity system 100 and flight crew personal electronicdevice 203. However, other secure wireless communication networkinterfaces are possible, such as a secure near-field wirelesscommunication protocol 213B and/or a secure Bluetooth wirelesscommunication protocol 213C, or other secure wireless communicationinterfaces. In one embodiment, flight crew personal electronic device203 is a wireless smart device, such as a tablet computer, a cellulardevice or other portable smart device capable of secure wirelesscommunication. Flight crew connectivity system 100 includes a dedicatedand secure IEEE 802.11 service set identifier for airline proprietarylogin for flight crew use only.

In one embodiment, USB controller 231 provides for a wired universalserial bus interface between controller 201 and personal electronicdevice 203. For example, USB controller 231 is connected to controller201 via data bus 228E and to personal electronic device 203 at a USBcommunication adapter port 239 (e.g., a wired data communication port).Personal electronic device 203 includes a universal serial bus interfaceadapter (e.g., a wired communication adapter) to connect to adapter port239. In this regard, personal electronic device 203 communicates withdata transceiver 211A and/or data transceiver 211B over a wired datacommunication path including controller 201 and USB controller 231. Insome embodiments, USB controller 231 includes an electrical chargingadapter to electrically charge personal electronic device 203 whenconnected to adapter port 239. The USB communication interface discussedherein presents one non-limiting embodiment of a wired datacommunication interface, and it is understood other wired datacommunication interfaces between personal electronic device 203 andflight crew connectivity system 100 may be contemplated.

In one embodiment, flight crew connectivity system 100 includes securedigital (SD) card controller 232 to provide for a secure digital (SD)card 235 (e.g., secure data memory card) interface. SD card controller232 provides for a data communication between flight crew personalelectronic device 203 and SD card 235. In this regard, SD cardcontroller 232 provides a communication interface to transmit and/orreceive data between personal electronic device 203 and SD card 235.

In one embodiment, cellular transceiver 215 provides for a securewireless communication interface between personal electronic device 203and a cellular communication tower 237. In some embodiments, cellulartransceiver 215 includes a subscriber identification module (SIM) 241 tosecurely store personal electronic device 203 subscriber identity. Inthis regard, cellular transceiver 215 provides a second secure wirelessnetwork 119 for secure communication between personal electronic device203 and external cellular device 237A. In some embodiments, applicationssoftware is provided from an operator at a remote location via thesecond secure wireless network 119 to upload flight operations software(e.g., such as updates to existing flight operations software) to one ormore of the avionics equipment 102 LRUs, such as the Flight ManagementComputer (FMC), for example. In this regard, the flight operationssoftware includes a unique identifier within the software header toidentify the particular LRU associated with the software, and thesoftware is either manually or automatically loaded into the LRU. Invarious embodiments, avionics equipment 102 provides a discreet signalto cellular transceiver 215 to disable communication between personalelectronic device 203 and external cellular device 237A when aircraft101 is airborne.

FIG. 3 illustrates various data domains within an aircraft fuselage 301in accordance with an embodiment of the disclosure. As illustrated inFIG. 3, aircraft fuselage 301 includes multiple aircraft data domains.For example, in some embodiments, fuselage 301 includes an aircraftcontrol domain 312, an aircraft information systems domain 314, apassenger information and entertainment system domain 316, and apassenger owned devices domain 318A-B.

In various embodiments, aircraft regulations require separation ofdirect access between one or more of the above domains. For example,aircraft control domain 312 and aircraft information systems domain 314require direct Ethernet connections be isolated from passengerinformation and entertainment system domain 316 and passenger owneddevices domain 318A-B. In various embodiments, flight crew connectivitysystem 100 provides flight crew members dedicated and secure wirelessaccess to one or more of these domains in flight deck 110 by physicallyisolating aircraft control domain 312 and/or aircraft informationsystems domain 314 from passenger information and entertainment systemdomain 316 and/or passenger owned devices domain 318A-B.

In some embodiments, avionics equipment 102 includes a Flight ManagementComputer (FMC), a Flight Data Acquisition Unit (DFDAU), a DisplayProcess Computer (DPC), a Proximity Sensor Electronics Unit (PSEU), anElectronic Flight Bag (EFB), a Cabin Connectivity System (CCS), and anOn-board Network System (ONS). The list is not exhaustive and, in otherembodiments, fewer or more units (e.g., line replaceable units (LRUs))may be included in avionics equipment 102. In some embodiments,non-avionics equipment 104 includes an In-Flight Entertainment andConnectivity System (IFEC) in communication with passenger owned devicesdomain 318 via less secure wireless access points (WAPs) 105A-D withinaircraft cabin 107. The list of non-avionics equipment 104 and/ornon-avionics features is not exhaustive and, in other embodiments, feweror more units and/or features may be included.

FIG. 4 illustrates various functions of a flight crew connectivitysystem 100 in accordance with embodiments of the disclosure. Asillustrated, flight crew connectivity system 100 provides flight crewmembers with dedicated and secure wireless access to many functionsincluded within domains 312, 314, 316, and 318 of aircraft 101.

For example, in some embodiments, a crew wireless function 422 providesfor a dedicated Wi-Fi network for data access by personal electronicdevice 203 within aircraft 101 for flight crew use only. A wirelessmaintenance function 424 provides flight crew members with maintenanceand troubleshooting data of aircraft systems over the flight crewdedicated Wi-Fi network 103A-C. A wireless data download function 426provides for download of airplane and maintenance data from avionicsequipment 102, such as ONS and DFDAU, to flight crew member's personalelectronic device 203. In some embodiments, a wireless data uploadfunction 428 provides for upload of flight plan information to the FMCand other data or information to various avionics equipment 102 fromflight crew member's personal electronic device 203.

In some embodiments, a wired data up/down function 430 provides for ahigh speed wired USB connection to flight crew member's personalelectronic device 203 for both upload and download tasks, and providesfast charging of personal electronic device 203 connected to adapterport 239 of USB controller 231. In some embodiments, a secure highspeed/broadband link 432 provides flight crew member's personalelectronic device 203 with a dedicated and secure high speed off-boardlink for download and upload of business and/or operational data. Forexample, flight crew member's personal electronic device 203 may beutilized for accessing weather data in anticipation of optimizingaircraft 101 flight route.

In some embodiments, a cellular data function 434 provides flight crewmembers with an alternate secure high speed off-board link for downloadand upload of operational and business data and loadable software, suchas application software for business and/or flight operations loadableto personal electronic device 203. The cellular link is disabled whilethe aircraft is airborne to comply with regulatory agency requirements.A Wi-Fi data function 436 provides flight crew member's personalelectronic device 203 with an alternate secure high speed offboard linkfor download and upload of business and operational data. A networksecurity function 438 is implicit through the mutually exclusive accessto aircraft control domain 312, aircraft information systems domain 314,passenger information and entertainment system domain 316 via domainswitch 223. A secure memory module 440 provides for localized storage ofoperational data via secure digital card 235. Additional features mayinclude, in some embodiments, near-field 213B and/or Bluetooth 213Cwireless communication protocols used for communication between flightcrew connectivity system 100 and personal electronic device 203.

FIG. 5 illustrates a panel concept display (or display panel) 500 for aflight crew connectivity system 100 in accordance with embodiments ofthe disclosure. In some embodiments, flight crew connectivity system 100is a form fit for installation in a panel within flight deck 110, forexample. In this regard, flight crew connectivity system 100 is intendedto meet criteria specific to flight deck requirements, such as: switchtypes, switch positions, lights, colors, font, and symbols. Flight crewconnectivity system 100 integrated control and operation are initiatedvia an ON/OFF switch 540 to enable or disable the system to broadcastits secure wireless signal, such as a Wi-Fi wireless signal fromwireless data transceiver 213, for example. In some embodiments, displaypanel 500 includes an indicator light 225, implemented as a lightemitting diode (LED), for visual indication that the system is turned onand transmitting. In other embodiments, indicator 225 is implemented asan audible signal or other type of indicator to inform an operator thesystem is turned on and transmitting. Another feature includes amulti-position switch to choose between avionics switch position 542 andIFEC switch position 544. The first switch position 540 would turn offflight crew connectivity system 100 to comply with regulations that mayrequire non-flight critical devices to be turned off in the event of anemergency. Avionics switch position 542 (highest level of security),enables a link to aircraft avionics equipment 102 data, but does notallow the flight crew to access non-avionics equipment 104, such as thebroadband SATCOM system. IFEC switch position 544 (lowest level ofsecurity), enables flight crew to access the IFEC for connection tobroadband internet applications, and does not allow the flight crew toaccess avionics equipment 102.

In some embodiments, a fourth switch position is installed and isimplemented by a rotary type switch, for example. The fourth switchposition is used for loading aircraft control computers, such aswirelessly uploading a flight plan to the FMC from personal electronicdevice 203. In various embodiments, the fourth switch position isisolated from the other switch positions (e.g., switch positions 542and/or 544) that link to avionics equipment 102 data and IFEC. In someembodiments, a USB adapter port 239 is installed with a wired dataconnection to provide a wired connection between flight crewconnectivity system 100 and personal electronic device 203. In someembodiments, adapter port 239 is used to electrically charge personalelectronic device 203. In some embodiments, flight crew connectivitysystem 100 includes cellular transceiver 215 including, for example, a 3g/4 g cellular modem and SIM card 241, to allow personal electronicdevice 203 to communicate with a cellular mobile device via cellulartower 237, when aircraft 101 is on the ground.

FIGS. 6A-B illustrate flow diagrams describing a method for using aflight crew connectivity system 100 in accordance with an embodiment ofthe disclosure.

In block 601, flight crew connectivity system 100 is powered on. In thisregard, switch 540 on display panel 500 is used to switch power toflight crew connectivity system 100. Switch 540 on display panel 500controls power switch 219 connected between aircraft power module 106and flight crew connectivity system 100 to power on and power off flightcrew connectivity system 100.

In block 603, after powering on, flight crew connectivity system 100forms a wireless communication connection between data transceiver 213and personal electronic device 203 (e.g., external communicationdevice). In some embodiments, a secure Wi-Fi wireless interface 213A isused as a wireless connection between flight crew connectivity system100 and flight crew personal electronic device 203. However, othersecure wireless communication connections are possible, such as a securenear-field wireless communication connection 213B and/or a secureBluetooth wireless communication connection 213C. In some embodiments,flight crew connectivity system 100 includes a dedicated and secure IEEE802.11 service set identifier for airline proprietary login for flightcrew use only.

In block 605, flight crew member determines whether to communicate withavionics equipment 102 or non-avionics equipment 104. In this regard,flight crew member selects avionics switch position 542 on display panel500 to communicate with avionics equipment 102 or IFEC switch position544 to communicate with non-avionics equipment 104.

In block 607, if flight crew member chooses avionics switch position542, domain switch 223 is moved to first output terminal 223A to switchpower to first data transceiver 211A (e.g., first data interface device)coupled to avionics equipment 102. Powered on data transceiver 211Areceives data from avionics equipment 102 via data bus 221C implementedas an aircraft proprietary ARINC 429 data bus, an aircraft proprietaryARINC 717 data bus and/or an Ethernet interface. Data transceiver 211Amay communicate with one or more units associated with avionicsequipment 102, as discussed herein.

In block 609, controller 201 forms a secure data communication pathbetween data transceiver 211A (e.g., first data interface device) anddata transceiver 213 via data buses 228A and 228C. For example, domainswitch 223 isolates power to data transceiver 211A only, whilemaintaining data transceiver 211B in an off state. Thus, communicationbetween data transceiver 211A and avionics equipment 102 is isolated ondata buses within flight crew connectivity system 100.

In block 611, flight crew connectivity system 100 provides for one ormore units associated with avionics equipment 102 to securelycommunicate avionics data between data transceiver 211A (e.g., firstdata interface device) and data transceiver 213 for personal electronicdevice 203 (e.g., external communication device). In this regard,avionics equipment 102 is physically isolated on data buses 228A and228C, and wireless communication connection between data transceiver211A and personal electronic device 203 is a dedicated and secure IEEE802.11 service set identifier (SSID) airline proprietary login forflight crew personal electronic device 203 use only.

In block 613, flight crew member selects IFEC switch position 544 ondisplay panel 500 to communicate with non-avionics equipment 104.

In block 615, if flight crew member chooses IFEC switch position 544,domain switch 223 is moved to second output terminal 223B to switchpower to data transceiver 211B (e.g., second data interface device)coupled to non-avionics equipment 104. Powered on data transceiver 211Breceives data from non-avionics equipment 104 via data bus 221Dimplemented as an Ethernet data bus to complement Ethernet interface115.

In block 617, controller 201 forms a secure data communication pathbetween data transceiver 211B (e.g., second data interface device) anddata transceiver 213 via data buses 228B and 228C. As discussed herein,domain switch 223 isolates power to data transceiver 211B only, whilemaintaining data transceiver 211A in an off state. Thus, communicationbetween data transceiver 211B and non-avionics equipment 104 is isolatedon data buses within flight crew connectivity system 100. In thisregard, security is maintained for avionics equipment 102 within flightcrew connectivity system 100.

In block 619, flight crew connectivity system 100 provides for one ormore units associated with non-avionics equipment 104 to securelycommunicate non-avionics data between data transceiver 211B (e.g.,second data interface device) and data transceiver 213 for personalelectronic device 203 (e.g., external communication device). In thisregard, non-avionics equipment 104 is physically isolated on data buses228B and 228C, and wireless communication connection between datatransceiver 211B and personal electronic device 203 is a dedicated andsecure IEEE 802.11 service set identifier (SSID) airline proprietarylogin for flight crew personal electronic device 203 use only.Communication with non-avionics equipment 104 provides for flight crewmembers to access broadband internet on their personal electronic device203 and/or communicate with external cellular users, for example.

Where applicable, various embodiments provided by the present disclosurecan be implemented using hardware, software, or combinations of hardwareand software. Also where applicable, the various hardware componentsand/or software components set forth herein can be combined intocomposite components comprising software, hardware, and/or both withoutdeparting from the spirit of the present disclosure. Where applicable,the various hardware components and/or software components set forthherein can be separated into sub-components comprising software,hardware, or both without departing from the spirit of the presentdisclosure. In addition, where applicable, it is contemplated thatsoftware components can be implemented as hardware components, andvice-versa.

Software in accordance with the present disclosure, such as program codeand/or data, can be stored on one or more computer readable media. It isalso contemplated that software identified herein can be implementedusing one or more general purpose or specific purpose computers and/orcomputer systems, networked and/or otherwise. Where applicable, theordering of various steps described herein can be changed, combined intocomposite steps, and/or separated into sub-steps to provide featuresdescribed herein.

Embodiments described above illustrate but do not limit the invention.It should also be understood that numerous modifications and variationsare possible in accordance with the principles of the present invention.Accordingly, the scope of the invention is defined only by the followingclaims.

What is claimed is:
 1. A system comprising: one or more data interfacedevices configured to communicate data; a power module configured toprovide power to the one or more data interface devices; a switchcoupled between the power module and each of the one or more datainterface devices and configured to selectively provide power from thepower module to at least one of the one or more data interface devices;a data transceiver configured to couple to an external communicationdevice; and a controller coupled between the one or more data interfacedevices and the data transceiver and configured to provide a datacommunication path between the selectively powered data interface deviceand the data transceiver for the external communication device.
 2. Thesystem of claim 1, wherein the one or more data interface devicescomprises: a first data interface device configured to communicate withavionics equipment when the first data interface device is powered,wherein the avionics equipment is configured to provide aircraft controland aircraft information data; and a second data interface deviceconfigured to communicate with non-avionics equipment when the seconddata interface device is powered, wherein the non-avionics equipment isconfigured to provide broadband internet access and/or passengerinformation and entertainment data.
 3. The system of claim 2, whereinthe aircraft control and aircraft information data is physicallyisolated on the data communication path when the first data interfacedevice is powered and the second data interface device is unpowered, andwherein the broadband internet access and/or the passenger informationand entertainment data is physically isolated on the data communicationpath when the second data interface device is powered and the first datainterface device is unpowered.
 4. The system of claim 2, wherein thedata transceiver comprises a wireless data transceiver configured toprovide a secure wireless communication network for the externalcommunication device.
 5. The system of claim 4, wherein the externalcommunication device comprises one or more wireless smart devicesconfigured to communicate with the wireless data transceiver via thesecure wireless communication network.
 6. The system of claim 5, furthercomprising a cellular transceiver comprising a second secure wirelesscommunication network configured to communicate between the one or morewireless smart devices and an external cellular device, wherein thesecond secure wireless communication network is configured tocommunicate application software comprising business and/or flightoperations to the one or more wireless smart devices and/or the avionicsequipment.
 7. The system of claim 2, wherein the external communicationdevice is configured to communicate data to the avionics equipment viathe data communication path when the first data interface device ispowered, and wherein the avionics equipment is configured to communicateflight information to the external communication device via the datacommunication path when the first data interface device is powered. 8.The system of claim 1, further comprising a universal serial buscontroller coupled to the controller configured to provide a wired datacommunication path for the external communication device, wherein theexternal communication device comprises a wired communication adapterconfigured to couple to a universal serial bus controller datacommunication port to form the wired data communication path.
 9. Thesystem of claim 8, wherein the universal serial bus controller furthercomprises an electrical charging adapter configured to electricallycharge the external communication device coupled to the datacommunication port, and further comprising a secure digital cardcontroller configured to communicate between a secure data memory cardand the external communication device to provide for secure data storagewithin the secure data memory card.
 10. An aircraft comprising thesystem of claim 1, wherein the aircraft comprises: avionics equipment;non-avionics equipment; a power source configured to provide power; anda power source switch coupled between the power source and the powermodule configured to selectively switch power from the power source tothe power module.
 11. A method of using the system of claim 2, themethod comprising: selectively switching power from the power module tothe at least one of the one or more first and second data interfacedevices; coupling the first data interface device to the avionicsequipment when the first data interface device is powered; coupling thesecond data interface device to the non-avionics equipment when thesecond data interface device is powered; forming the data communicationpath between the powered data interface device and the data transceiver;validating a security level of the external communication device; andcommunicating the data between the powered data interface device and thedata transceiver for the external communication device.
 12. A method ofincorporating the system of claim 1 into an aircraft, the methodcomprising: installing the one or more data interface devices, the powermodule, the controller, and the data transceiver, wherein the controlleris coupled between the one or more data interface devices and the datatransceiver; and coupling the switch between the power module and eachof the one or more data interface devices.
 13. A method comprising:selectively switching power from a power module to at least one of oneor more data interface devices to selectively power the at least onedata interface device; forming a data communication path between theselectively powered data interface device and a data transceiver; andcommunicating data between the selectively powered data interface deviceand the data transceiver for an external communication device.
 14. Themethod of claim 13, wherein the one or more data interface devicescomprises: a first data interface device configured to communicate withavionics equipment, wherein the avionics equipment is configured toprovide aircraft control and aircraft information data; and a seconddata interface device configured to communicate with non-avionicsequipment, wherein the non-avionics equipment is configured to providebroadband internet access and/or passenger information and entertainmentdata, the method further comprising: identifying the selectively powereddata interface device; and communicating the identified selectivelypowered data interface device to the external communication device. 15.The method of claim 14, wherein communicating data further comprises:communicating data between the first data interface device and theavionics equipment when the first data interface device is powered; andcommunicating data between the second data interface device and thenon-avionics equipment when the second data interface device is powered.16. The method of claim 14, further comprising: physically isolating theaircraft control and aircraft information data on the data communicationpath when the first data interface device is powered and the second datainterface device is unpowered, and physically isolating the broadbandinternet access and/or the passenger information and entertainment dataon the data communication path when the second data interface device ispowered and the first data interface device is unpowered.
 17. The methodof claim 13, wherein the data transceiver comprises a wireless datatransceiver, and wherein communicating data further comprises forming asecure wireless communication network for the external communicationdevice.
 18. The method of claim 17, wherein the external communicationdevice comprises one or more wireless smart devices, and whereincommunicating data further comprises communicating data between the oneor more wireless smart devices and the wireless data transceiver via thesecure wireless communication network.
 19. The method of claim 18,further comprising a cellular transceiver comprising a second securewireless communication network coupled to the wireless data transceiver,wherein forming a data communication path further comprises forming asecond data communication path between the one or more wireless smartdevices and an external cellular device via the second secure wirelesscommunication network, wherein the second secure wireless communicationnetwork is configured to communicate application software comprisingbusiness and/or flight operations to the one or more wireless smartdevices and/or avionics equipment.
 20. The method of claim 13, furthercomprising a universal serial bus controller configured to provide awired communication path, wherein the external communication devicecomprises a wired communication adapter configured to couple to auniversal serial bus controller data communication port, wherein thecommunicating data further comprises communicating via the datacommunication port for the external communication device, and whereinthe method further comprises charging the external communication devicecoupled to the universal serial bus controller via the datacommunication port, and the communicating further comprisescommunicating data between a secure data memory card and the externalcommunication device to provide for secure data storage within thesecure data memory card.